home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / e / misc.xsave / 000138_2damn@nospam.com_Mon Dec 17 11:41:47 2007.msg < prev    next >
Internet Message Format  |  2020-01-01  |  2KB
  1. Path: reader1.panix.com!panix!newsfeed.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!newscon04.news.prodigy.net!prodigy.net!newsdst01.news.prodigy.net!prodigy.com!postmaster.news.prodigy.com!newssvr14.news.prodigy.net.POSTED!cb3c0661!not-for-mail
  2. From: 2damn <2damn@nospam.com>
  3. Subject: Re: Screen Capture
  4. Newsgroups: comp.protocols.kermit.misc
  5. References: <h654j.66697$RX.26340@newssvr11.news.prodigy.net>
  6.     <MPG.21c0aebcb13143f798977e@news.bellatlantic.net>
  7.     <VTI7j.77731$YL5.64694@newssvr29.news.prodigy.net>
  8.     <MPG.21cea210be52e49b989780@news.bellatlantic.net>
  9. User-Agent: Pan/0.129 (Benson & Hedges Moscow Gold)
  10. MIME-Version: 1.0
  11. Content-Type: text/plain; charset=UTF-8
  12. Content-Transfer-Encoding: 8bit
  13. Lines: 12
  14. Message-ID: <hAk9j.24861$4V6.5609@newssvr14.news.prodigy.net>
  15. NNTP-Posting-Host: 68.127.120.160
  16. X-Complaints-To: abuse@prodigy.net
  17. X-Trace: newssvr14.news.prodigy.net 1197856141 ST000 68.127.120.160 (Sun, 16 Dec 2007 20:49:01 EST)
  18. NNTP-Posting-Date: Sun, 16 Dec 2007 20:49:01 EST
  19. Organization: SBC http://yahoo.sbc.com
  20. X-UserInfo1: Q[R_PJSCOXUOR_\YMZHXOTDB]R_LAFHLVP\FNLUL@@\FWOUNDO_AR\J[WDXJHVKHGFFIZHBL@FX\NIOC@FWYNV\DMNS[HTLIXX\^BUGBXLR@PB@\FKCLXSWAIDFOKG^MFT[GZN^NWY_GVLSRGDYY^AW_MS_RW][KBYZMADO@Y[ABPSPE_TA@LTLFXVTC@RJM
  21. Date: Mon, 17 Dec 2007 01:49:01 GMT
  22. Xref: panix comp.protocols.kermit.misc:15721
  23.  
  24. On Sun, 16 Dec 2007 07:48:12 +0000, John Santos wrote:
  25. > I believe there is an escape sequence that can be sent to the terminal
  26. > to do the same thing as pressing the "print screen" key.  I didn't want
  27. > to complicate the original post by going into that.  If your program
  28. > knows when to screen scrape, it can send the sequence at the appropriate
  29. > time.  If the program doesn't know when to do it, and the user has to
  30. > press a key.  Otherwise, how do you expect it to happen?
  31.  
  32. This is a great suggestion I had not really considered. I will try it out 
  33. this week.
  34.  
  35.